Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: introduce lisk sepolia #33

Merged
merged 4 commits into from
Feb 18, 2025
Merged

Conversation

juliopavila
Copy link
Contributor

Description:

This PR adds support for the Lisk Sepolia testnet in Hardhat configuration. The newly introduced network allows deploying and verifying smart contracts on Lisk's Sepolia blockchain.

Changes:

  • Added lisk-sepolia network configuration to hardhat.config.ts.
  • Included lisk-sepolia under the etherscan.apiKey configuration using a placeholder key.
  • Extended customChains configuration to support contract verification for Lisk Sepolia.

Deployment and Verification:

The following contracts were successfully deployed on Lisk Sepolia:

References:

Copy link
Member

@auryn-macmillan auryn-macmillan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@auryn-macmillan
Copy link
Member

We should perhaps squash that failing unit test that's blocking CI

@coveralls
Copy link

Pull Request Test Coverage Report for Build 13393313492

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 97.778%

Totals Coverage Status
Change from base Build 10633798941: 0.0%
Covered Lines: 50
Relevant Lines: 50

💛 - Coveralls

@juliopavila juliopavila merged commit 3d0fc08 into main Feb 18, 2025
2 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants